home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d8
/
vmix225.arc
/
VMIX.DOC
< prev
next >
Wrap
Text File
|
1990-05-21
|
54KB
|
1,016 lines
_______
____|__ | (tm)
--| | |-------------------
| ____|__ | Association of
tm | | |_| Shareware
VMiX 386 Version 2.25 |__| o | Professionals
----------------------- -----| | |---------------------
|___|___| MEMBER
Copyright (c) 1986, 1987, 1988, 1989
Commercial Software Associates
Post Office Box 185
Corona del Mar, California 92625
BBS (714) 721-1228 (24 Hrs.)
VOICE (714) 721-9953 (8 - 6pm PDT)
_______________________________________________________________
| |
| WHAT IS VMiX? |
| |
| VMiX is a multitasking and multiuser environment for |
| IBM PC's and PS/2's (PC, XT, AT, PS/2) compatibles. |
| |
| Version 2.25 configures itself to your processor. If you |
| have an 8088 or 8086, then your applications must share |
| the 470 Kbytes available after VMiX loads in low memory. |
| If you have an 80286, then VMiX can multitask applica- |
| tions that use expanded memory or can swap applications |
| to extended memory. Swapped tasks will be swapped back |
| regularly for a timeslice of the processing or they can |
| remain suspended until reactivated. |
| |
| If you have an 80386, VMiX will multitask in extended |
| memory. It will execute each task in virtual 8086 mode, |
| with protected mode pagging, mapping a new 640 Kbytes to |
| each new task. |
| |
| Multitasking is supported at the console, in windows or |
| full screen. If you do not like windows at your console |
| you can choose to use terminals or PC's attached to the |
| COMM ports. |
| |
| The VMiX environment uses the best from MSDOS and UNIX |
| in its implementation of the user control shell and |
| multitasking. The user has a choice of 2 user interfa- |
| ces: the VMiX shell, which can talk to the MSDOS shell |
| (you get both sets of commands), or the VMiX pull-down |
| menus interface. |
| |
| Applications that do not write directly to the video, |
| like DBASE, TURBO PASCAL, PROCOMM, WSTAR, WORDPERFECT, |
| OPUS BBS, or BASIC will display correctly at a terminal. |
| |
| VMiX co-resides with DOS 2.1 through 4.01 |
|_______________________________________________________________|
_______________________________________________________________
| |
| HOW TO INSTALL VMiX? |
| |
| VMiX is easy to install. Simply copy the executable |
| files in the VMiX archive to your directory and execute |
| the boot module VM_BOOT.EXE |
| |
| There are 3 start-up options, if VMiX fails to start |
| correctly on your computer. VM_BOOT -r will force 8086 |
| VMiX mode on 80286 or 80386 computers, and VM_BOOT -x |
| will force 80286 VMiX mode on 80386 computers. Using |
| VM_BOOT -l or VM_BOOT -lx will inhibit relocation of |
| portions of VMiX to extended memory. Use of these 3 |
| options might allow VMiX to execute in your environment. |
| |
| Later you will learn how to customize your VMiX start-up |
| by including command arguments in the VM_BOOT command |
| line from DOS. |
|_______________________________________________________________|
_______________________________________________________________
| |
| HOW TO INSTALL MY APPLICATIONS? |
| |
| If you can execute your applications from DOS, they |
| are already installed for VMiX. VMiX does not use PIF |
| or other types of application configuration files. |
| |
| Applications that write directly to the screen can |
| coexist with other applications at the console, but |
| will not display properly at a COMM port terminal or PC. |
|_______________________________________________________________|
_______________________________________________________________
| |
| HOW MUCH MEMORY WILL REMAIN AFTER VMiX IS INSTALLED? |
| |
| On a 640Kb memory 8088 PC or 80286 AT with DOS 3.1 and |
| no installed TSR's, there will remain about 470Kb of |
| memory for applications. On the 80386, each task gets |
| it's own 640Kb from your extended memory pool. |
|_______________________________________________________________|
_______________________________________________________________
| |
| HOW DO I VALIDATE THAT VMIX IS WORKING CORRECTLY ON MY |
| SYSTEM? |
| |
| To test VMiX, we recommend that you perform the two |
| tests below: |
| |
| TEST 1: Validates that VMiX itself is working correctly. |
| |
| invoke VMiX as follows: (from the directory where you |
| copied VM_BOOT.EXE ) |
| |
| vm_boot do /debug set |
| |
| and PRESS <ENTER> |
| This will start 2 tasks: |
| the root shell or main |
| window, where the key- |
| board will remain unless |
| you press <SHIFT><TAB>, |
| |
| a VMiX debugger task |
| displaying information |
| about the 'set' command. |
| If all windows display activity, the TEST PASSED. |
| From the root window type 'quit' and press <ENTER>|
| to exit VMiX. |
| |
| |
| TEST 2: Validates that VMiX, your version of MSDOS, and |
| your system's ROM BIOS, all get along fine. |
| |
| invoke VMiX as follows: (from the directory where you |
| copied VM_BOOT.EXE ) |
| |
| vm_boot do dir c: /type c:\autoexec.bat |
| |
| and PRESS <ENTER> |
| This will start 2 tasks: |
| the root shell or main |
| window, displaying your |
| autoexec.bat file, where |
| the keyboard will remain,|
| |
| and another task doing a |
| directory. |
| If all windows display activity, the TEST PASSED. |
| From the root window type 'quit' and press <ENTER>|
| to exit VMiX. |
|_______________________________________________________________|
_______________________________________________________________
| |
| WHAT IS UNIQUE ABOUT VMiX? |
| |
| VMiX is supported shareware. In the rapidly developing |
| multitasking market, VMiX has undergone over 15 new |
| releases in the last 3 years, each with new and enhanced |
| features. |
| |
| VMiX provides an easy to install and operate environment |
| that can be used to multitask DOS. It can also be used |
| to simply task switch applications to extended memory on |
| an 80286/386 PC. |
| |
| VMiX also provides remote access to your multitasking PC |
| server. |
| |
| VMiX gives you more than a multitasker, it gives you an |
| operating system which gently introduces you to the new |
| complexities of advanced systems. |
| |
| If you can execute your applications from DOS, they are |
| already installed for VMiX. VMiX does not use PIF or |
| other types of application configuration files. |
| |
| The VMiX command interface is layered, to protect the |
| casual user who just wants to get maximum utility and |
| does not need or wants to learn the full system. |
| For the serious operator or software developer, VMiX |
| provides an internal 'debug' shell which can be coupled |
| with a DOS debugger or tool, as a concurrently executing |
| VMiX task, to examine other live applications, DOS, or |
| VMiX itself. |
|_______________________________________________________________|
_______________________________________________________________
| |
| SAMPLE STARTUP |
| ----- if your printer, mouse, or modem is on COM1, |
| then COM2 is available for user logins: |
| (NOTE the lower case 'L', below) |
| |
| C> vm_boot set remote -l2 |
| |
| |
| ----- if your printer, mouse, or modem is on COM2, |
| then COM1 (VMiX default) is available for logins: |
| |
| C> vm_boot |
| |
| |
| ----- if you are using both COM1 and COM2, |
| then set VMiX to COM3 to avoid interferance: |
| (NOTE the lower case 'L', below) |
| |
| C> vm_boot set remote -l3 |
| |
| |
| ----- if you want to start with the VMiX pull-down |
| menus: |
| |
| C> vm_boot vw |
|_______________________________________________________________|
_______________________________________________________________
| |
| QUICK START TO VMiX MULTITASKING |
| |
| The VMiX manual is big and spread out, but the last |
| 2 chapters describe each VMiX command in detail. |
| |
| Basically these are the commands that you must master |
| FIRST, to start using the multitasking features right- |
| away. |
| |
| |
| ? Pressing '?' will display a list of avail- |
| able VMiX commands. Typing a VMiX command |
| that requires additional parameters, will |
| display usage information. |
| |
| |
| exec This command allows you to partition the |
| use of your PC's memory between tasks. |
| By default, VMiX partitions each new MSDOS |
| task into 224Kb chunks of available memory, |
| on 8088 and 80286 processors. On the 80386 |
| the default partition size is 512Kb. |
| |
| To override the defaults, you might type: |
| exec -m128 |
| |
| this sets the partition size to 128Kb. |
| Any new program, after that, will only see |
| a maximum of 128Kb available, until the next|
| 'exec -m' reduces or expands the current |
| limit. |
| |
| In 80386 processors, selecting a partition |
| size smaller than the 512Kb default, will |
| cause new tasks to use the parent's memory |
| partition and will not be mapped to their |
| own 640Kb, from the extended memory pool. |
| |
| |
| do This command allows you to specify a new |
| MSDOS task. 'do' is short for 'dosjob'. |
| To execute BASIC in a window, you would |
| type: |
| do c:\basic |
| |
| To execute BASIC and give it the full |
| screen, you would type: |
| do -W c:\basic |
| |
| 'do' is the basic VMiX command to start a |
| new and separate process. |
| |
| Shift TAB Once you have started several windows, you |
| will need to move the keyboard between them,|
| so that input to each task can be safely |
| directed to only that task. You move the |
| keyboard, in round-robin fasion by pressing |
| the Shift and Tab keys simultaneously. |
| Shift Tab will also clear any defunct |
| windows left around, when there remains |
| only one shell active. |
| |
| do /rshell To clone the VMiX command shell into a 2nd |
| shell, you type: |
| do /rshell |
| |
| The / tells VMiX this is not a command for |
| MSDOS but for VMiX. VMiX will ask you for |
| a login name, type: |
| su |
| |
| This is a reserved name for a VMiX operator |
| with 'kill' process priviledges. |
| |
| do . To clone an MSDOS command shell as the 2nd |
| window, you type: |
| do . |
| |
| To close the window, type from MSDOS: |
| exit |
| |
| NOTE THAT THE VMiX SHELL PROMPT DIFFERS |
| FROM THE MSDOS SHELL PROMPT IN THE SINGLE |
| SPACE THAT FOLLOWS THE PROMPT. |
| From the VMiX Shell |
| a directory request would look like |
| C> dir |
| From MSDOS it would look like |
| C>dir |
| |
| $$ Particularly in 386 mode, you might find |
| that some programs might crash VMiX or fail |
| to execute correctly. To provide system |
| protection, when executing an ill-behaved |
| program, precede the filename and path |
| with the characters '$$': |
| $$[drive:][path]filename |
| or, |
| do $$[drive:][path]filename |
| |
| |
| NOW THAT YOU KNOW EVERYTHING, YOU CAN CHOOSE TO FORGET |
| ALL ABOUT IT AND USE, INSTEAD, THE VMiX PULL-DOWN MENUS |
| BY TYPING, AFTER VMiX STARTS: |
| |
| C> c:\vmix\vw |
| |
| |
| REMEMBER THAT ANY COMMAND YOU CAN GIVE FROM INSIDE VMiX |
| CAN ALSO BE STATED IN THE VM_BOOT COMMAND LINE, EACH |
| COMMAND SEPARATED BY A / |
| |
| Congratulations, you are now a certified VMiX SysOp. |
|_______________________________________________________________|
_______________________________________________________________
| |
| WHAT IS AHEAD FOR VMiX? |
| |
| A larger 80386 partition size. |
| Virtual 386 video screens to avoid bleed-thru |
| by applications that write directly to video. |
| A new serial port V.42 data link driver. |
| A distributed file system: |
| 'rshell' to allow one VMiX PC to execute as a |
| client of a server VMiX at another PC. |
| This will allow one PC to multi-task on its |
| screen a program executing at a second PC. |
|_______________________________________________________________|
RELEASE NOTES
* See the revision.log file for enhancements and bug fixes to this version.
In Summary Version 2.25 provides:
1. This is the first non BETA release of VMiX.
VMiX now works on the IBM PS/2 and COMPAQ 386 SX.
2. Added support for ESDI fixed disk systems.
3. Made some more fixes related to DOS 4.01 multitasking.
Reduced resident memory size by 8Kbytes.
The VMiX prompt now displays the current directory.
4. VMiX is now one of the fastest MSDOS multitaskers. The preemptive
scheduler is now fully sensitive to I/O. The following devices affect
the executing priority of a task: keyboard, disk drives, COMM ports.
5. The VMiX start-up program 'VM_BOOT' has three command line switches
that control the mode the program runs. Using VM_BOOT -r, will force
VMiX into real (8086) mode and using VM_BOOT -x, will force VMiX into
extended (80286) mode. These 2 command line switches, disable 80386
protected mode operations. (Useful for getting around compatibility
problems, on certain computers.) Using VM_BOOT -l or VM_BOOT -lx
inhibits relocation of portions of VMiX to extended memory.
6. Version 2.25 will operate with DOS 4.01. Since DOS 4.01 can be set to
use extended memory, conflicts can arise. VMiX must be told how much
extended memory other programs are using (see 12.d, below).
7. The VMiX clock tick has been changed from 55msec (18.2 task switches
per second) to 11msec (90.9 task switches per second). A new command,
'set system -c ????' will allow you to tune your multitasking environ-
ment for maximum efficiency. The command specifies the number of clock
ticks a running task is guarranteed to be active before preemption.
(Refer also to the 'chprio' command.)
8. The Shift-Tab hot key will now swap screens between graphics mode
tasks and alphanumeric mode tasks. Also, tasks using different video
pages will be switched correctly. This affects only tasks that were
started with the 'dosjob -W' (full screen) command. NOTE that this
version of VMiX still does not trap programs that make direct video
RAM write. Now that the multitasker is complete we will start to
correct the video messup by ill-behaved MSDOS software.
9. When using VMiX in 80386 mode, the memory partition size is set auto-
matically to 512Kb, at boot time. If you use the command 'exec -m' to
set a partition size less than 512Kb, VMiX will not request extended
memory for new task partitions until you issue 'exec -m512' again.
When the partition size is less than 512Kb, VMiX uses memory from the
parent process for the new task (same as 8088 and 80286 mode).
The default partition size for all other VMiX modes remains 224Kb.
10. The new '?' command, lists the available VMiX shell commands.
The 'set dos -m' command has been removed, since the VMiX shell is
now always transparent to DOS commands. MSDOS commands are passed
to 'command.com' and VMiX commands are passed to VMiX.
11. The new command 'examine status' displays information about a task,
including available memory. Other memory status commands include
'examine mcb' and 'monitor -p'.
12. IMPORTANT NOTICE: We have found that the following reasons are the
most frequent causes of VMiX 386 failure:
a) Cable connected to COM1 port which causes VMiX port
test to hang. Recommend to test VMiX with serial
cable disconnected during vm_boot process. Make
a new cable as described in the VMiX manual.
b) The contents of your CONFIG.SYS specify a device
driver that uses extended memory in conflict
with VMiX. (for example, SMARTDRV.SYS, HIMEM.SYS)
c) Failure to reassign VMiX's default port for user
logins, COM1, to another port number when COM1 is
already in use (modem, mouse, etc.). Recommend to
start VMiX with a non-existent port for logins:
(NOTE the lower case 'L', below)
vm_boot set remote -l4 (ie., COM4)
d) Using 'swap' with an extended memory cache program
installed, when VMiX has not been told to reserve
in-use extended memory with the debugger shell
command:
'assign memory ????'
where ???? is number of bytes to reserve above
1 Megabyte (ie., 500000 bytes will be rounded
up to the nearest multiple of 4Kbytes).
e) Using an ANSI.SYS driver that does not support
discreet window scrolling, but instead, always
scrolls the entire screen. Quarterdeck Office
System supplied DVANSI.COM (for DESQview) works
correctly with VMiX 386.
f) Using VMiX with DOS 4.01 on some 386 computers
will boot OK, but multitasking will be erratic
or lock the system.
g) The following vendor's 386 computers are known
to crash (incompatible) or not crash (compatible)
VMiX during 386 protected mode start-up:
Incompatible Compatible
--------------- -------------------
CompuAdd 386 AST Premium 386
HP Vectra 386 AT&T 386
Zenith 386 Cheetah cAT 386-20
COMPAQ 386-25
COMPAQ 386-SX
Everex 386-16
Everex Step 386-25
Gateway 2000 386-20
Micronics 386
Monolithic 386-16
Northgate 386
Olivetti 386-20
PS/2 70-80
Tandy 5000
IMPORTANT IMPORTANT IMPORTANT
--------- --------- ---------
N O T I C E
The manual included in the non-registered distribution diskette is the
last ASCII version of the VMiX manual. This manual, describes the use of
VMiX Versions 1.4X. It should be sufficient to allow you to fully test
VMiX. All changes to VMiX, since its introduction April 1987, are logged
in the revision.log file, including the new features in Version 2.25.
The VMiX COMMAND LOOK-UP - QUICK REFERENCE, shown below, is the current
list of all VMiX Version 2.25 commands and syntax. VMiX provides built-
in help, as described in the 1.4X manual.
If you decide that VMiX is the way to go, please register, and we will
ship to you the new printed manual for version 2.XX, and the source code
to the VMiX utilities and Application Programmer's Interface to VMiX.
Additionally, you will receive the eight user version and a version
optimized for the 80386 instruction set.
We appreciate the comments and help of all the users, who through
various BBS's helped debug VMiX. Thanks!
QUICK OVERVIEW
* VMiX is not presently a full operating system. It provides the services
of a multiuser operating system supervisor. The VMiX kernel ties tightly
between the host operating system I/O services and the user applications.
The eventual goal of the VMiX kernel is to arbitrate the use of system
resources by individual tasks with either or both UNIX I/O or DOS I/O,
in an environment providing up to 16 megabytes of physical memory.
* The console screen can be automatically partitioned into up to four
windows, for a total of 4 tasks executing from the console. The active
task controls and responds to the console keyboard. The active task
can be switched, at any time, by pressing the hot key, Shift-Tab.
* VMiX does not need to operate in protected mode to multitask. Hence, it
can be used in 8088 PCs. In 80286 mode, VMiX ocassionally needs to use
protected mode for swapping. In 80386 mode, VMiX operates in protected
mode at all times. System services are provided in SYSGATE.ASM to execute
your own functions in protected mode. The debugger "assign gdt" method
allows entries to the VMiX GDT. This can also be done with the memory
manager system service.
* REMOTE permits a user to call a remote PC running VMiX, and teleoperate,
as if he were at the console of the remote PC. Useful for remote customer
support of application programs, offsite login and operations. VMiX
terminal drivers provide full CGA text mode emulation at a COMM port.
* With VMiX you can run programs like WINDOWS, LOTUS 123, XTALK, BASIC,
DBASE, or WORD at the console and BASIC, DEBUG, TURBO PASCAL, WORDSTAR 3.2,
WORDSTAR 4.0, WordPerfect 4.X, PROCOMM, or DBASE II/III at a COMM terminal.
Multiple BASIC or GWBASIC interpreter sessions are supported.
* Supports a maximum of five users (only because of COMM port limitations),
each with multiple processes up to a maximum of 8 total.
* SPAWN or '&' permits a script of VMiX shell commands to be submitted to a
background process executing the VMiX shell. This allows for background
jobs like compiling or printing by a concurrent child process.
* DOSJOB permits keyboard interactive applications to be partitioned and
managed as concurrent video display tasks.
* Loadable character fonts, 33 line CGA display and 43 line EGA/VGA display.
Version 2.25 provides support for EGA/VGA video modes and up-to 58 line
display, with VMiX font type 1.
* As explained in the manual, there are (4) four ways to execute a .BAT,
.COM, or .EXE program:
with 'exec' (now optional),
with a command line trailling '&',
with 'spawn',
or (the easiest way) with the 'dosjob' command.
When VMiX starts, unless you issued an 'exec -m<size in Kbytes>' at the
command line, VMiX will use memory partitions of 224Kb for (8088/80286)
programs or partitions of 512Kb in 80386 processors.
The 'exec -m ????', memory partitioning command, is intended for use
mainly on 8086 and 80286 computers, which can not use the VMiX 386 virtual
memory manager. This command guarantees that a second or third program
will find some memory available. The user can select, from the shell,
the partition size for any single program. If your system has 640Kb
memory, then the command 'exec -m192' will only let programs grab memory
to a maximum of 192Kb each. If you need to execute DOS commands like
'exec type <filename>' or 'exec dir', then setting 'exec -m128' should
provide enough memory for about 4 DOS shells in non-80386 systems.
* To use 'dosjob' to execute a VMiX shell command(s) in a separate console
window, precede the command with a / (ie., 'dosjob /debug' or 'dosjob
/rshell'). The / must not be used if the command is for DOS, for example
'do basica' or 'do dir'.
To use 'dosjob' to run a program that requires access to the full screen,
use the '-W' option (ie., 'dosjob -W [drive:][path]filename').
* The VMiX scheduler can provide interrupt corruption protection to multiple
executing tasks. This prevents, to some degree, changes effected by one
task to the system interrupt table from interferring with the interrupts
handlers expected by a second task. To request protection for an ill-
behaved program, precede the filename and path with the characters '$$'.
Programs using protection will execute slower. Some programs like
BASIC/BASICA and WINDOWS, automatically receive protection without '$$'.
The command syntax is:
exec $$[drive:][path]filename
or,
dosjob $$[drive:][path]filename
* VMiX can be started with the command line switches -r, -x, -l, or -lx.
These switches affect the mode that VMiX executes in and overrides internal
configuration defaults. This option allows VMiX to be downgraded and used
with some compatibles, which can not run VMiX protected mode functions.
The command syntax is:
VM_BOOT [-l] [-r] [-x] [ [ command ] /... ]
where,
the '-r' option forces 8088 (real mode) operation on 80286/386 cpu's.
the '-x' option forces 80286 (real/protected mode) operation on 80386.
the '-l' option inhibits relocation of VMiX code to extended memory.
the '-lx' option is a combination of the above.
* Console operator status line 'set video -s'
* Built-in debugger 'debug' 'monitor -r'
* Memory manager and memory mapper 'monitor -m' 'monitor -p' 'examine mcb'
* User specified windows at either the console or VT-100 COMM terminal.
* Assembly and High Level Language interface.
* Interrupt 15h VMiX System Services.
Today VMiX is 90Kb of code and 20Kb of Kernel data.
75% Microsoft C and 25% MASM.
VMiX is (C) Copyrighted 'try before you purchase software'. This gives us
wide distribution for a low cost, thus keeping your purchase price also low.
When you are ready to register your version, or require:
pricing for support, the programming interface documentation, the new full
printed manual, the source code, corporate pricing, or other information,
please contact us.
Enjoy exploring VMiX and thanks
for supporting its development,
Tony Borras
Commercial Software Associates
Post Office Box 185
Corona del Mar, California 92625
BBS (714) 721-1228 (24 Hrs.)
VOICE (714) 721-9953 (8 - 6pm PST)
----------------------------------------------------------------------------
The VMiX 386 System consists of the 29 files described below.
These files reside in the three self-extracting distribution archives:
VMIX???.EXE (Shareware distribution ??? version id)
VMIX386.EXE (Registered Owners ONLY)
VMIXUTL.EXE (Registered Owners ONLY)
EXECUTABLE or OBJECT FILES
- VM_BOOT.EXE -
The VMiX start-up program. To start, type VM_BOOT from DOS's C>
prompt and press <ENTER>.
- VM_BSML.EXE -
A smaller version of VMiX, if your applications do not need graphics
support.
- DPATH.EXE -
Utility executed by user to set the directory search PATH for data files.
Use DOS 'PATH =' or 'SET PATH =' for executable files.
Use VMiX 'DPATH =' or 'SET DPATH =' for data files.
- DSTAT.EXE -
Utility executed by user to view device and channel status.
- MONITOR.EXE -
Debugging utility executed by user to examine memory and processes.
- OUTSIDE.EXE -
Outside MSDOS shell spawning utility for BBS operators.
- PS.EXE -
Utility executed by user to view process status.
- VW.EXE -
Utility executed by user to add a pull-down menu interface to the VMiX
shell.
- SYSGATE.OBJ -
Link object file for VMiX API (Application Programming Interface).
SOURCE FILES DOCUMENTATION FILES
SYSGATE.ASM READ.ME
DSTAT.C VMiX.DOC(this file)
DPATH.ASM REVISION.LOG(upgrade history)
MONITOR.C DPATH.DOC
OUTSIDE.C MANUAL.DOC(version 1.4X)
PS.C
VW.C
C_BIOS.H
$_KERNEL.H
$_CONFIG.H
$_MEM.H
$_PROC.H
IO_CHAN.H
IO_IRP.H
IO_OBJ.H
I N S T R U C T I O N S
-----------------------
1) Upon receipt of your SHIPPING
Diskette, copy the six files:
VM_BOOT.EXE, DPATH.EXE, DSTAT.EXE,
MONITOR.EXE, PS.EXE and VW.EXE onto
your own System Diskette or hard
disk.
2) Using your editor, create a file
named CONFIG.SYS. Include the
following two lines:
BUFFERS = 15 (or more)
FILES = 20 (or more)
and, save the file to your system
boot disk.
3) To execute the VMiX 386 program
requires MSDOS Version 2.25 or
above, and 256Kb of memory. A color
graphics card, VGA is recommended
for the console display.
If you have a Monochrome Adapter,
VMiX will sense it.
Release 2.25 does not operate in
386 protected mode at all times, so
it will execute properly in PCs
with 8088 processors.
Start VMiX by typing:
C> VM_BOOT <ENTER>
After VMiX starts, typing a '?'
will display all the available
commands.
Try: debug <ENTER>
(note the prompt changes to - )
then, try 'set' or 'exam' and
VMiX will display how to complete
the command. VMiX will prompt
for most command line arguments,
when not included in the command
line:
Try: set video -m <ENTER>
to see the video modes available,
or
set term -t <ENTER>
to see the terminals supported.
4) To start VMiX 386 with pull-down
menus:
Start VMiX by typing:
C> VM_BOOT VW <ENTER>
When VMiX starts, the top screen
line will display the available
menus. Move to the desired menu
by pressing right or left arrow
keys. Select a menu by pressing
the down arrow key or by typing
the CAPITALIZED letter of the
menu name. Select a menu option
with the down arrow and press
<ENTER>.
Exit from the vw utility or pull-
down menu with the <Esc> key.
From a terminal running VW.EXE,
use <Ctrl><F> to turn function
key emulation ON, then backspace
becomes left arrow, <Ctrl><J>
and <Ctrl><K> will act as down
and up arrow.
5) The RS232 cabling for COM1 and/or
COM2 should be constructed
depending on whether the host PC
will be connected to a dumb
terminal or to another PC acting as
a terminal.
PIN PIN
H 1 1
O
S 2 -- - _ _ _ - -- 2
T -_ __ - -
3 __ _ - - - - _ __ 3 T
S E
e 4 4 R
r M
i --5 5 I
a -| N
l | --6 6 A
| L
P | 7 ------------------------- 7
o |
r | --8 8
t -|
--20 20
See Part II, Using VMiX 386, for
detailed instructions regarding the use
of VMiX 386 commands and options.
----------------------------------------------------------------------------
VMiX COMMAND LOOK-UP - QUICK REFERENCE
|ROOT |DEBUG |
|LEVEL..|LEVEL..|LEVEL............................|
| 0 | 1 | 2 |
---------------------------------------------------
|[debug] |
| |set |
| |baud |
| -c " sets communications: chan|
| baud, parity, word, stop"|
| |dos |
| -i " toggles DOS child process|
| file inherit ON/OFF" |
| -n " sets DOS INT21 function |
| maximum nesting level" |
| -p " sets DOS current process |
| PSP: nuPSP(seg)" |
| -s " sets DOS virtual size: |
| (4Kb blocks)" |
| |font |
| -t " sets font type: (0 - 3)" |
| |pool |
| -a " adjusts program memory: |
| MCB(seg), nusize(para)" |
| -m " sets program partition |
| size: (0 - 1024Kb)" |
| -o " sets program memory |
| owner: MCB(seg), |
| nuPSP(seg)" |
| |process |
| -b " sets process shell buffer|
| size: (0 - 127)" |
| -e " toggles system evironment|
| protection ON/OFF" |
| -h " toggles process hardware |
| priviledge ON/OFF" |
| -s " toggles process system |
| priviledge ON/OFF" |
| |remote |
| -c " sets remote channel" |
| -l " sets polled terminal |
| login channel" |
| |system |
| -c " sets duration of task |
| slice: tickcnt - 1" |
| -m " toggles manager message |
| displays ON/OFF" |
| -s " toggles scheduler swapped|
| processing ON/OFF" |
| -t " toggles scheduler clock |
| processing ON/OFF" |
| -w " sets shutdown wait delay:|
| seconds" |
| |terminal |
| -t " sets terminal type: |
| (0 - 9)" |
| |video |
| -c " sets video bg/fg colors" |
| -C " sets window bg/fg colors"|
| -m " sets video mode:(0 - 16)"|
| -s " toggles status line |
| display ON/OFF" |
| -w " sets root window size: |
| row0, col0, row1, col1" |
| -W " auto partitions (1 - 4) |
| task windows |
| (Shift-Tab toggles kbd)" |
| |init |
| |comm |
| -c " sets communications: chan|
| baud, parity, word, stop"|
| |print |
| -p " inits parallel port:chan"|
| |examine |
| |mcb |
| |status |
| |assign |
| " : process id, channel" |
| |gdt |
| |deassign |
| " : channel" |
| |gdt |
| |memory |
| |quit |
|rshell |
|remote |
| -c " sets remote channel" |
| -l " sets polled terminal login channel" |
|swap |
| " : process id" |
|chprio |
| " : process id, new priority" |
|[exec] |
| -a " adjusts program memory: MCB(seg), |
| nusize(para)" |
| -m " sets program memory partition size: |
| (0 - 1024Kb)" |
| -o " sets program memory owner: MCB(seg), |
| nuPSP(seg)" |
| |path " utility displays/sets |
| program file search path"|
| |dpath[.exe] " utility displays/sets |
| data file search path" |
| -v " sets verbose mode (default)" |
| -q " sets quiet mode" |
| -r " allows data read only" |
| -w " allows data read/write (default)"|
| -h " help" |
| |dstat[.exe] " utility displays all |
| VMiX objects" |
| -a " selects only assigned objects" |
| -r " selects only free objects" |
| |monitor[.exe] " utility monitors process/|
| system: process id" |
| -m " displays 1 megabyte memory map" |
| -p " displays VMiX memory pool" |
| -r " monitors process registers: |
| process id" |
| |ps[.exe] " utility displays all |
| processes" |
| |vw[.exe] " VMiX pull-down menu |
| utility" |
| " : MSDOS command" |
|dosjob |
| " : MSDOS command or / VMiX command" |
| [-W] " gives process the full screen: MSDOS |
| command or / VMiX command" |
|spawn |
| -c " sets channel for STDIO and executes |
| command line" |
|kill |
| " : process id" |
|quit |
---------------------------------------------------
: indicates command parameters
[ ] indicates optional
VMiX TERMINAL - IBM FUNCTION KEY EMULATION
---------------------------------------------------
|Press ^F (1 beep) emulation ON |
|Press ^F again (2 beeps) emulation OFF |
| |
| |
| for press |
| |
| IBM PC KEY TERMINAL KEY |
| |
| [F1] 1 |
| [F2] 2 |
| [F3] 3 |
| [F4] 4 |
| [F5] 5 |
| [F6] 6 |
| [F7] 7 |
| [F8] 8 |
| [F9] 9 |
| [F10] 10 |
| |
| <Ctrl>[Break] ^C |
| <Ctrl>[NumLock] ^S |
| <Ctrl>[F3] ` |
| [PgUp] + |
| [PgDn] - |
| [Ins] ^I |
| [Del] ^D |
| [End] ^E |
| [Home] [Home] |
| <Alt> <Shift> |
| |
| |
| |
| NOTE: The <Ctrl> key symbol for the terminal |
| keyboard has been abbreviated as ^ |
| |
---------------------------------------------------
